Skip to content

[AUTO] Increment version to 2.19.6.#20864

Merged
andrross merged 2 commits into2.19from
create-pull-request/patch-2.19
Mar 16, 2026
Merged

[AUTO] Increment version to 2.19.6.#20864
andrross merged 2 commits into2.19from
create-pull-request/patch-2.19

Conversation

@opensearch-trigger-bot
Copy link
Contributor

I've noticed that a new tag 2.19.5 was pushed, and incremented the version from 2.19.5 to 2.19.6.

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@opensearch-trigger-bot opensearch-trigger-bot bot requested a review from a team as a code owner March 13, 2026 18:29
@github-actions
Copy link
Contributor

PR Code Analyzer ❗

AI-powered 'Code-Diff-Analyzer' found issues on commit 64660b1.

PathLineSeverityDescription
libs/core/src/main/java/org/opensearch/Version.java153mediumV_2_19_6 is assigned the version ID 20190699, which does not follow the established numeric pattern (V_2_19_3=2190399, V_2_19_4=2190499, V_2_19_5=2190599). The expected value is 2190699. The extra leading digit causes this version to be numerically much larger than all prior versions, which could corrupt version comparison logic, break backward compatibility checks, or cause CURRENT to appear far ahead of any known version. While likely a typo, the impact on version ordering and the fromId() lookup warrants investigation to rule out intentional tampering with version detection.

The table above displays the top 10 most important findings.

Total: 1 | Critical: 0 | High: 0 | Medium: 1 | Low: 0


Pull Requests Author(s): Please update your Pull Request according to the report above.

Repository Maintainer(s): You can bypass diff analyzer by adding label skip-diff-analyzer after reviewing the changes carefully, then re-run failed actions. To re-enable the analyzer, remove the label, then re-run all actions.


⚠️ Note: The Code-Diff-Analyzer helps protect against potentially harmful code patterns. Please ensure you have thoroughly reviewed the changes beforehand.

Thanks.

Signed-off-by: Andrew Ross <andrross@amazon.com>
@github-actions
Copy link
Contributor

❌ Gradle check result for 1a60c1a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

✅ Gradle check result for 1a60c1a: SUCCESS

@codecov
Copy link

codecov bot commented Mar 14, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.00%. Comparing base (e582a51) to head (1a60c1a).
⚠️ Report is 3 commits behind head on 2.19.

Additional details and impacted files
@@             Coverage Diff              @@
##               2.19   #20864      +/-   ##
============================================
+ Coverage     71.95%   72.00%   +0.04%     
- Complexity    65989    66004      +15     
============================================
  Files          5342     5342              
  Lines        307360   307361       +1     
  Branches      44857    44857              
============================================
+ Hits         221167   221315     +148     
+ Misses        67736    67548     -188     
- Partials      18457    18498      +41     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@andrross andrross merged commit d2b513e into 2.19 Mar 16, 2026
49 of 51 checks passed
@andrross andrross deleted the create-pull-request/patch-2.19 branch March 16, 2026 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants